Dashboard
The dashboard primarily focuses on the display of feed/chain pairs that have gone out of deviation or when the pair's heartbeat has been exceeded. It also shows alert-able wallet balances as well as the last hour of the Loki log records.
Pairs
Use the Pairs tab to view feed/chain pairs that are out of deviation or have exceeded their heartbeat. Each of the six timestamped status columns of the table represents an execution cycle of the historyWorker that runs every minute to detect deviations and exceeded heartbeats.
There are three controls atop the pairs table.
- Opens the legends dialog which explains what each icon in the pairs table represents.
- Network group pick list. Switches between All chains, Mainnets, and Testnets.
- Toggle to show data for external validators.
Meta data column
There are four components in the meta data column stacked top to bottom.
- The pair's deviation threshold.
- The pair's heartbeat time limit in minutes.
- The subscription end date of the pair.
- The number of validators used to calculate deviations (P1 and P5).
Status columns (6)
The status columns show the AirseekerRegistry price for the pair and the price from each validator assigned to the pair. It also show icons related to the state of the pair's on-chain AirseekerRegistry price. See the next section Legends for explanation of the icons.
Legends
- Status badges (validators): Colored dots, one for each validator. These denote a validator which is outside the deviation threshold for the pair when compared to its
AirseekerRegistryvalue. - Heart icon: The heartbeat has been exceeded for the pair.
- Bell (orange) icon: A P1 deviation alert was sent which indicates a deviation with the internal validator
signed_dataand the pair'sAirseekerRegistryvalue. - Bell (grey) icon: A P5 deviation alert was sent which indicates a deviation with all external validators and the pair's
AirseekerRegistryvalue. The pair must have more than one external validator to trigger this alert. - Question mark (yellow) icon: The dashboard failed to retrieve the subscription data shown in the Meta data column.
- Up or Down arrows (green) icon: An
AirseekerRegistryupdate to the pair's price occurred near to the timestamp of run cycle. - Eye icon: Info message. These messages are not critical to any P1 alert but could impact lower level alerts.
- Exclamation circle icon: Warning message. These messages could impact any alert including P1 deviation.
- Exclamation triangle icon: Error message. These errors indicate errors that resulted during code execution.
- X icon: Insufficient data. There must be at least six columns of data to support the display of data for each pair. The lack of data is rare and (outside of development) should be reported.
Deviations
An alert is generated for deviation issues if sustained for three consecutive cycles (minutes) because:
- The price is out of deviation with signed data for each cycle AND
- the price of the data feed has not changed for each cycle.
In the image below for ETH/USD on Taiko, an OpsGenie alert was raised because the signedData indicator (orange dot) appears in 3 consecutive run cycles and the price did not change. This means that Airseeker did not update the price for some reason.
In the image below an OpsGenie alert was not generated for KAVA/USD on Kava because during the three consecutive run cycles shown, the price of KAVA/USD changes each cycle. This means that Airseeker changed the price with each cycle. Note the price/deviation values in each cycle shows that as soon as the Airseeker update was made the feed's value went out of deviation again because the signedData value from the API providers medium price also change.
Heartbeats
An alert is generated for heartbeat issues if sustained for three consecutive cycles (minutes) because:
- The price of the data feed has not been updated.
Wallets
This tab shows any sponsor or fallback wallet on mainnets that has a critical balance. See the Wallets page within the Centurion UI for a full list of wallets.
RPC
This tab shows a list of RPC URLs that are deemed unhealthy by the multiCall.js. See multiCall for conditions that will mark the URL as unhealthy.
Loki
This tab shows the log records (INFO and ERROR) from the workers. These are best used to understand OpsGenie alerts when related. The log records are helpful when a particular chain is having issues.